Write data mask method and system

ABSTRACT

In various embodiments, dedicated mask pins are eliminated by sending a data mask on address lines of the interface. A memory controller receives a request for a memory write operation from a memory client and determines the granularity of the write data from a write data mask sent by the client. Granularity, as used herein, indicates a quantity of write data to which each bit of the received write data mask applies. In an embodiment, the memory controller generates a particular write command and a particular write data mask based on the granularity of the write data. The write command generated is typically the most efficient of several write commands available, but embodiments are not so limited. The write command is transmitted on command lines of the interface, and the write data mask is transmitted on address lines of the interface.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 11/509,143, filed Aug. 23, 2006, which is incorporated by reference as if fully set forth.

TECHNICAL FIELD

The invention is in the field of data transfer in computer and other digital systems.

BACKGROUND

As computer and other digital systems become more complex and more capable, methods and hardware to enhance the transfer of data between system components or elements continually evolve. Data to be transferred includes digital signals representing data, commands, addresses, or any other information. System components or elements can include different functional hardware blocks on a single integrated circuit (IC), or on different ICs. The different ICs may or may not be on the same printed circuit board (PCB). System components typically include an input/output (I/O) interface specifically designed to receive data from other system components and to transmit data to other system components.

One consistent trend as computing systems become more capable is an increase in the amount of data to be transferred per time period. Some applications that require high data rates include game consoles, high definition television (HDTV), personal computers (PCs) main memory, graphics processors, and various consumer devices not already mentioned. In response to the demand for increased data rates, double data rate (DDR) standards have been developed to standardize the behavior of hardware and software using high data rates. Several generations of graphics DDR (GDDR) standards have been developed specifically for graphics processing and video processing, which typically demand the capability to transfer and process very large amounts of data.

In some instances, it is necessary to write only a portion of the bits in a transmission. For example, in a system that transmits 32 bytes, or 256 bits per command, some but not all of the 32 bytes might be written in a write operation. This will be referred to as a byte-write operation herein. One conventional byte-write method is to read the 256 bits that are in the DRAM, modify the portion to be changed, and write all of the 256 bits back. This method is commonly used in central processing units (CPUs), and is referred to as a read-modify-write operation. Unfortunately, for high-speed applications, such as graphics applications, read-modify-write operations are both too slow and too complex to implement. One reason is that graphics processors often use a complex operation reordering schemes in order to optimize the memory interface.

So historically DRAMs provide one additional data mask pin for every eight data pins, which indicates whether the eight bit data should be written or not. This data mask method is referred to in existing DRAM specifications. One disadvantage of this method is it results in one extra pin for every eight data bit pins, thus increasing the pin count.

In addition, the existing data mask method in existing DRAM specifications is not applicable in high speed interfaces which are susceptible to data bit errors. One reason is that the errors on the data mask pins are fatal. This is due to the fact that an error on the data mask pin may result in a byte write that was not intended. The data in that byte would be destroyed (overwritten) and could not be retried. In addition, an error on the data mask will make the error detection/correction feature provided by certain DRAMs useless.

FIG. 1A is a block diagram of components of a prior art digital system 100. The components include a processor 102 and a memory component 104. The processor 102 controls the memory component 104 by communicating over an interface that includes command lines, address lines, data lines, and separate, dedicated data mask lines. The memory component 100 is a DDR memory that communicates with the processor 102 over a DDR interface.

FIG. 1B is a timing diagram illustrating a write operation 106 with a data mask, as performed by the prior art components of FIG. 1A. In this illustration, a burst-of-8 write transaction has been issued. The top waveform is the clock (CLK) waveform. The waveform below the CLK waveform shows the command waveform (CMD) on the command lines. Three write commands are shown, write 108, write 110 and write 112. The data waveform is shown below the command waveform. In each of the valid data periods labeled 1-8, eight bits of data are transmitted. A data mask waveform is shown below the data waveform. The data mask waveform indicates the values being transmitted on the data mask lines. For write 108, the data mask line is high during the entire write. In this illustration, a low data mask bit, or a 0 logic level on a data mask line, indicates that the corresponding byte is to be written. So, for write 108, none of the bytes 108 are to be written.

Write 110 differs from write 108. Write 110 is a byte-write in which only particular bytes of the eight bytes are to be written. Referring to the data mask waveform for write 110, it can be seen that the data mask has a value of 10110111 Therefore, data mask pins and lines are required to be available for each write operation, even if byte-write operations make up a small percentage of write operations, as is often the case in many modern applications.

One approach to allowing byte-writes without the use of a dedicated mask pin is a reusable data mask. In DRAMs that support this capability, a memory controller can program the data mask into a register inside the DRAM and reuse it later. However, for many applications, including many graphics application, the number of reusable mask is small, so the performance improvement may not be very great.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of components of a prior art digital system.

FIG. 1B is a timing diagram illustrating a write operation with a data mask, as performed by the prior art components of FIG. 1A.

FIG. 2 is a block diagram of elements of a system, according to an embodiment.

FIG. 3 is a timing diagram illustrating a write operation with a write_without_mask command, according to another embodiment.

FIG. 4 is a timing diagram illustrating a write operation with a write_multiple_mask command, according to an embodiment.

FIG. 5 is a timing diagram illustrating a write operation with a write_single_mask command, according to an embodiment.

FIG. 6 is a flow diagram of a method performed by a memory controller, according to an embodiment.

FIG. 7 is a flow diagram of a method performed by a memory device, according to an embodiment.

FIG. 8 is a diagram showing an alternative mapping of write data mask bits to data bytes according to an embodiment.

In the drawings, the same reference numbers identify identical or substantially similar elements or acts. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the Figure number in which that element is first introduced (e.g., element 102 is first introduced and discussed with respect to FIG. 1).

DETAILED DESCRIPTION

A method an apparatus for efficiently performing byte-write via a high-speed memory interface is described herein. As used herein a byte-write is a write of less than all of the data accommodated by a command cycle on the high-speed memory interface. In various embodiments, dedicated mask pins are eliminated by sending a data mask on address lines of the interface. A memory controller receives a request for a memory write operation from a memory client and determines the granularity of the write data from a write data mask sent by the client. Granularity, as used herein, indicates a quantity of write data to which each bit of the received write data mask applies. In an embodiment, the memory controller generates a particular write command and a particular write data mask based on the granularity of the write data. The write command generated is typically the most efficient of several write commands available, but embodiments are not so limited. The write command is transmitted on command lines of the interface, and the write data mask is transmitted on address lines of the interface. In the case of some write commands, circumstances, no additional cycles are required to perform a byte-write.

FIG. 2 is a block diagram of elements of a system 200 according to an embodiment. The system 200 includes a memory controller 202 and a memory device 208. In an embodiment, the memory device 208 is a double data rate dynamic random access memory (DDRAM), but embodiments are not so limited. The memory controller 202 includes data mask logic 204 and selection logic 206. The memory controller 202 receives requests for memory access from various memory clients (not shown) in the system 200. As further described herein, the data mask logic examines write requests received and determines whether they include a write mask. If a received write request includes a write mask, the data mask logic determines which one of multiple data mask types should be used in performing the write operation. A write data mask type implies both a write data mask and a corresponding write command, as further described below. In an embodiment, the write data mask type is chosen based on which type would be most efficient, but in an alternative embodiment, the requester could specify a write data mask type.

When a write data mask type is determined, the data mask logic 204 generates the appropriate data mask associated with the write data and transmits it to the selection logic 206. The appropriate write command is generated as shown. In addition, the address associated with the write command is transmitted to the selection logic 206. The data mask logic 204 also generates a sel_data_mask signal that selects either the address or the data mask to be transmitted to the memory device 208 on the address lines of the interface.

The memory device 208 includes data mask logic 210 that receives the command on the command lines, the address and write data mask on the address lines. The data mask logic 210 determines from the command whether there is a write data mask, and also how to interpret the write data mask. Write data logic 212 receives the write data on data lines of the interface and also receives appropriately interpreted mask data from the data mask logic 210. The mask data includes individual bits that are interpreted to apply to one or more bytes of write data. In an embodiment, a bit of mask data that applies to one or more particular bytes of write data is a 0 if the one or more particular bytes are to be written to data array 214, and the bit of mask data is a 1 if the one or more particular bytes are not to be written to the data array 214. Other coding schemes are equally applicable.

FIGS. 3-5 are timing diagrams used to illustrate the write commands and write data masks according to data mask types of particular embodiments. FIGS. 3-5 are specific examples offered for the purpose of thoroughly describing the claimed invention, but they are not intended to be limited in any way. For example, in FIGS. 3-5 a high-speed memory interface that transfers 32 bytes of data per command is illustrated, but embodiments are applicable to other interface designs. An example protocol illustrated by FIGS. 3-5 is a graphics double-data-rate (GDDR) protocol such as GDDR5.

FIG. 3 is a timing diagram illustrating a write operation with a write_without_mask command, referenced as WOM. At the top of the diagram is a clock (clk) waveform showing the clock signal relevant to transmissions on the memory interface. A command line waveform (CMD) shows transmissions on the command lines. An address line waveform (ADDR) shows transmissions on the address lines. A data waveform (DATA) shows transmissions on the data lines.

One complete write operation will be described with reference to the first write_without_mask command, WOM0, although additional, similar write operations are shown in FIG. 3. The memory controller 202 has determined that there is no write data mask associated with a write request received from a memory client. Therefore, all bytes of data that are transmitted in the write operation are to be written to the memory device 208. The address associated with the WOM0 is 16 bits divided into 8 low address bits (A0L) and 8 high address bits (A0H). In an embodiment, a “no-operation” or NOP command follows WOM0. Here, we assume the specific application is doing a long burst of write, such that a NOP is inserted here to avoid data bus corruption. This NOP is not required by DRAM protocol, but will appear for many applications. Accordingly, the address lines are idle for the remainder of the available cycle time. In response to WOM0, 32 bytes of data D00-D31 are transmitted on the data lines of the interface and all are written to the memory device 208.

FIG. 4 is a timing diagram illustrating a write operation with a write_multiple_mask command, referenced as WDM in this example. The WDM command implies two bytes of data per write data mask bit as further described (“write double mask”), but in other embodiments the number could be three or more bytes of data per write data mask bit.

At the top of the diagram is a clock (clk) waveform showing the clock signal relevant to transmissions on the memory interface. A command line waveform (CMD) shows transmissions on the command lines. An address line waveform (ADDR) shows transmissions on the address lines. A data waveform (DATA) shows transmissions on the data lines.

One complete write operation will be described with reference to the first write_multiple_mask command, WDM0, although additional, similar write operations are shown in FIG. 4. The memory controller 202 has determined that there is a write data mask associated with a write request received from a memory client. The memory controller has further determined that the granularity of the write data is two bytes. That is, one bit of the write data mask applies to two bytes of write data. The address associated with the WDM0 is 16 bits divided into 8 low address bits (A0L) and 8 high address bits (A0H). In an embodiment, a “no-operation” or NOP command follows WDM0. This NOP is not required by DRAM protocol, but will appear for many applications. This available cycle time is used to transmit the write data mask as two 8-bit data mask portions, DDM00 and DDM01. Thus, in this case no additional time or pins are required to convey write data mask information to the memory device 208. In response to WDM0, 32 bytes of data D00-D31 are transmitted on the data lines of the interface and various bytes are written to the memory device 208 according to the write data mask. The write data mask includes 16 bits, each of which applies to a particular pair of bytes. That is, each write data mask bit is set or cleared to indicate whether or not to write a particular pair of bytes to the memory 208.

FIG. 5 is a timing diagram illustrating a write operation with a write_single_mask command, referenced as WSM in this example. The WSM command implies one bit of write data mask per write data byte.

At the top of the diagram is a clock (clk) waveform showing the clock signal relevant to transmissions on the memory interface. A command line waveform (CMD) shows transmissions on the command lines. An address line waveform (ADDR) shows transmissions on the address lines. A data waveform (DATA) shows transmissions on the data lines.

One complete write operation will be described with reference to the first write_single_mask command, WSM0, although additional, similar write operations are shown in FIG. 5. The memory controller 202 has determined that there is a write data mask associated with a write request received from a memory client. The memory controller has further determined that the granularity of the write data is one byte. That is, one bit of the write data mask applies to one byte of write data. The address associated with the WSM0 is 16 bits divided into 8 low address bits (A0L) and 8 high address bits (A0H). In an embodiment, a “no-operation” or NOP command follows WSM0. This NOP is not required by DRAM protocol, but will appear for many applications.

The write data mask associated with the WSM0 is 32 bits divided into four 8-bit portions, DM00, DM01, DM02, and DM03.

This available cycle time afforded by the NOP command is used to transmit DDM00 and DDM01. An additional NOP command is inserted to allow the transmission of DDM02 and DDM03. Thus, in this case there is a penalty for using such a fine granularity, but in various cases this is justified. In response to WSM0, 32 bytes of data D00-D31 are transmitted on the data lines of the interface and various bytes are written to the memory device 208 according to the write data mask. The write data mask includes 32 bits, each of which applies to a particular byte. That is, each write data mask bit is set or cleared to indicate whether or not to write a particular byte to the memory 208.

In various common applications, such as graphics applications, WDM and WOM will be used a great percentage of the time, due in part to the prevalence of 16-bit granularity data. In the case of a “mandatory” NOP cycle after a write command, the WDM command causes no performance degradation. Although the NOP cycle is not mandatory, in many applications such as graphic applications, the NOP is required to avoid data bus contention. So in most such applications any performance degradation is insignificant.

FIG. 6 is a flow diagram of a method 600 performed by a memory controller such as the memory controller 202 according to an embodiment. At 602, the memory controller determines whether a request received from a memory client is a write request. If the received request is a write request, the memory controller then determines at 604 whether a data mask is needed. In an embodiment, the memory controller reads a data mask supplied by the client in the request, but embodiments are not so limited. If a data mask is not needed, the memory controller issues a WOM command and transmits the appropriate address bits at 606.

If a data mask is needed, the memory controller determines whether the granularity of the data mask is one byte at 608. If the granularity of the data mask is not one byte, the memory controller issues a WDM command and transmits the appropriate address bits at 610. If the granularity of the data mask is one byte, the memory controller issues a WSM command and transmits the appropriate address bits at 612.

In other embodiments, the granularity of the data mask could be more than two. In other embodiments, the desired data mask granularity and/or the desired write command could be specified by the client in the request.

FIG. 7 is a flow diagram of a method 700 performed by a memory device such as the memory device 208 according to an embodiment. At 702 the memory device determines whether it has received a WOM command. If the memory device received the WOM command, the memory device performs a write at 704 of all of the received data to a location indicates by received address bits.

If the memory device did not receive a WOM command, the memory device determines whether it has received a WDM command at 706. If the memory device received a WDM command, the memory device performs a write of particular pairs of bytes of write data as indicates by the write data mask at 708.

If the memory device did not receive a WDM command, the memory device determines at 710 that is has received a WSM command. The memory device then performs a write of particular bytes of write data as indicates by the write data mask at 712.

FIG. 8 is a diagram showing an alternative mapping of write data mask bits to data bytes for a WSM command according to an embodiment. FIG. 8 is an example mapping between a specific address bit (in a specific burst location) to a specific data bit (in a specific burst location) which it will serve as a mask bit for the address bit.

Aspects of the embodiments described above may be implemented as functionality programmed into any of a variety of circuitry, including but not limited to programmable logic devices (PLDs), such as field programmable gate arrays (FPGAs), programmable array logic (PAL) devices, electrically programmable logic and memory devices, and standard cell-based devices, as well as application specific integrated circuits (ASICs) and fully custom integrated circuits. Some other possibilities for implementing aspects of the embodiments include microcontrollers with memory (such as electronically erasable programmable read only memory (EEPROM)), embedded microprocessors, firmware, software, etc. Furthermore, aspects of the embodiments may be embodied in microprocessors having software-based circuit emulation, discrete logic (sequential and combinatorial), custom devices, fuzzy (neural) logic, quantum devices, and hybrids of any of the above device types. Of course the underlying device technologies may be provided in a variety of component types, e.g., metal-oxide semiconductor field-effect transistor (MOSFET) technologies such as complementary metal-oxide semiconductor (CMOS), bipolar technologies such as emitter-coupled logic (ECL), polymer technologies (e.g., silicon-conjugated polymer and metal-conjugated polymer-metal structures), mixed analog and digital, etc.

Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in a sense of “including, but not limited to.” Words using the singular or plural number also include the plural or singular number, respectively. Additionally, the words “herein,” “hereunder,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. When the word “or” is used in reference to a list of two or more items, that word covers all of the following interpretations of the word, any of the items in the list, all of the items in the list, and any combination of the items in the list.

The above description of illustrated embodiments of the system and method is not intended to be exhaustive or to limit the invention to the precise forms disclosed. While specific embodiments of, and examples for, the system and method are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. The teachings of the disclosure provided herein can be applied to other systems, not only for systems including graphics processing or video processing, as described above. The various operations described may be performed in a very wide variety of architectures and distributed differently than described. In addition, though many configurations are described herein, none are intended to be limiting or exclusive.

In other embodiments, some or all of the hardware and software capability described herein may exist in a printer, a camera, television, a digital versatile disc (DVD) player, a handheld device, a mobile telephone or some other device. The elements and acts of the various embodiments described above can be combined to provide further embodiments. These and other changes can be made to the system and method in light of the above detailed description.

In general, in the following claims, the terms used should not be construed to limit the system and method to the specific embodiments disclosed in the specification and the claims, but should be construed to include any processing systems and methods that operate under the claims. Accordingly, the system and method is not limited by the disclosure, but instead the scope of the method and system is to be determined entirely by the claims.

While certain aspects of the method and system are presented below in certain claim forms, the inventors contemplate the various aspects of the method and system in any number of claim forms. For example, while only one aspect of the system and method may be recited as embodied in computer-readable medium, other aspects may likewise be embodied in computer-readable medium. Accordingly, the inventors reserve the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the system and method. 

What is claimed is:
 1. A memory controller comprising: data mask logic that generates a data mask associated with write data transmitted on a data line that enables the write data to be written in the same number of cycles as a write command without a data mask; and selection logic that selectively transmits the data mask and address information associated with a command line on an address line; wherein the transmissions on the data, address, and command lines are transmitted to a memory device.
 2. The memory controller of claim 1 wherein the data mask logic generates the data mask based on a write request.
 3. The memory controller of claim 1 wherein the data mask logic generates the data mask based on efficiency.
 4. The memory controller of claim 1 wherein the data mask logic generates the data mask based on at least one provided instruction.
 5. The memory controller of claim 1 wherein the data mask logic instructs the selection logic as to the selection of the address information or data mask for the transmission.
 6. A method of processing signals in a memory controller, the method comprising: generating a data mask associated with write data transmitted on a data line that enables the write data to be written in the same number of cycles as a write command without a data mask; selectively transmitting the data mask and address information associated with a command line on an address line; wherein the transmissions on the data, address, and command lines are transmitted to a memory device.
 7. The method of claim 6 wherein the data mask is generated based on a write request.
 8. The method of claim 6 wherein the data mask is generated based on efficiency.
 9. The method of claim 6 wherein the data mask is generated based on at least one provided instruction.
 10. The method of claim 6 further comprising providing instruction to the selection logic as to the selection of the address information or data mask for the transmission.
 11. A memory device comprising: data mask logic that receives a command on a command line and an address and a data mask on an address line and interprets the data mask; and data logic that receives data on a data line and receives the interpreted data mask from the data mask logic; wherein based on the interpreted data mask, the data logic writes the received data in the same number of cycles as a write command without a data mask.
 12. The memory device of claim 11 wherein the data mask logic determines from the command whether there is a data mask and how to interpret the data mask.
 13. The memory device of claim 11 wherein the interpreted data mask includes at least one individual bit that is interpreted to apply to at least one byte of the data.
 14. A method of writing received data on a memory device, the method comprising: receiving a command on a command line; receiving an address and a data mask on an address line; interpreting the data mask with data mask logic; receiving data on a data line and the interpreted data mask from the data mask logic; and writing the received data based in the interpreted data mask in the same number of cycles as a write command without a data mask.
 15. The method of claim 14 further comprising determining based on the received command using the data mask logic whether there is a data mask and how to interpret the data mask.
 16. The method of claim 14 wherein the interpreted data mask includes at least one individual bit that is interpreted to apply to at least one byte of the data. 